[compiler] First cut at dep inference #31386
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Ahh I think what you might be observing is that we create scopes for hook calls, but then flatten them away. And so either you’re looking at the pre-flattened state or you’re looking at a later pass after we flatten to a labeled block. We want to get rid of the labeled block and truly flatten it as if there had never been a scope, though. So I would definitely code as if there could be other instructions in the block w the effect. |
No, that should only happen if there wasn’t an inline function expression. |
jbrown215
changed the title
compiler/packages/babel-plugin-react-compiler/src/Inference/InferEffectDependencies.ts
Show resolved
Hide resolved
compiler/packages/babel-plugin-react-compiler/src/Inference/InferEffectDependencies.ts
Show resolved
Hide resolved
| let newInstructions = [...block.instructions]; | ||
| let addedInstrs = 0; |
There was a problem hiding this comment.
let's do the pattern used elsewhere where we only allocate a new array if there's actually something to change. most blocks won't have effects.
| value.args[0].kind === 'Identifier' && | ||
| value.args.length === 1 |
There was a problem hiding this comment.
this is TypeScript's unsoundness peeking through (ie it assumes array indexing is non-nullable) - these checks need to be reordered, the first could fail if there are no args
compiler/packages/babel-plugin-react-compiler/src/Inference/InferEffectDependencies.ts
Show resolved
Hide resolved
| useEffect(() => { | ||
| console.log(foo); | ||
| console.log(bar?.baz); | ||
| console.log(bar.qux); | ||
| }); |
There was a problem hiding this comment.
can you add a reference to a global, and a local variable with a non-reactive value? they should be part of the function deps but not added as effect deps
This is for researching/prototyping, not a feature we are releasing imminently.
Putting up an early version of inferring effect dependencies to get feedback on the approach. We do not plan to ship this as-is, and may not start by going after direct
useEffectcalls. Until we make that decision, the heuristic I use to detect when to insert effect deps will suffice for testing.The approach is simple: when we see a useEffect call with no dep array we insert the deps inferred for the lambda passed in. If the first argument is not a lambda then we do not do anything.
This diff is the easy part. I think the harder part will be ensuring that we can infer the deps even when we have to bail out of memoization. We have no other features that must run regardless of rules of react violations. Does anyone foresee any issues using the compiler passes to infer reactive deps when there may be violations?
I have a few questions:
addedInstrsvariable that I use to make sure I insert the effect deps array temp creation at the right spot.